Validation of stored or incoming messages

ABSTRACT

A mobile device can save time by validating a stored message, which was previously unreadable, by utilizing a related message, which can be received at a much quicker rate. In accordance with some aspects, the mobile device can save time by validating the stored message by reading a new related message and subsequently re-reading or descrambling the stored message or its CRC. The first attempt to read the message might not be successful due to a scrambling information change or due to other reasons. The reason for the failure of the first attempt to read the message may be determined based on whether a later attempt to read the message with the same or a different scrambling information is successful.

BACKGROUND

I. Field

The following description relates generally to communication systems andmore particularly to message validation.

II. Background

Wireless communication systems have become a prevalent means by whichmajority of people worldwide have come to communicate. These systems maybe multiple-access systems capable of supporting communication withmultiple users by sharing the available system resources (e.g.,bandwidth and transmit power). Examples of such multiple-access systemsinclude code division multiple access (CDMA) systems, time divisionmultiple access (TDMA) systems, frequency division multiple access(FDMA) systems, orthogonal frequency division multiple access (OFDMA)systems, and other systems.

A typical wireless communication network (e.g., employing frequency,time, and code division techniques) includes one or more base stationsthat provide a coverage area and one or more mobile (e.g., wireless)terminals that can transmit and receive data within the coverage area. Atypical base station can concurrently transmit multiple data streams forbroadcast, multicast, and/or unicast services, wherein a data stream isa stream of data that can be of independent reception interest to amobile terminal. A mobile terminal within the coverage area of that basestation can be interested in receiving one, more than one, or all thedata streams carried by the composite stream. Likewise, a mobileterminal can transmit data to the base station or another mobileterminal.

In conventional systems, when a mobile device listens to a wirelesscommunication network (e.g., base station), some of the messages cantake a relatively long time to download. During this time, battery poweris wasted and performance issues, such as missed communications andsystems losses, can be incurred.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In accordance with one or more aspects and corresponding disclosurethereof, various aspects are described in connection with validatingstored or incoming messages through utilization of related incomingand/or stored messages. The messages are linked, through signatures,hashes, or other linking techniques. If an attempt to read the messageis unsuccessful, the message (or a portion of the message) is stored.The stored messages can be validated, at a later time, by readingsubsequent messages, which can be received at a quicker rate. Thestoring of messages that are unreadable can mitigate the time spentre-downloading large messages, which can increase standby time andperformance metrics, such as communication reception.

An aspect relates to a method for validating stored or incomingmessages. The method includes determining that a message was notsuccessfully read after a first attempt and retaining the message asunreadable. Scrambling information is obtained and an attempt to re-readthe message with the obtained scrambling information is performed. Themethod further ascertains whether the message was not successfully readafter the first attempt due to a scrambling information change or due toa reason different from a scrambling information change.

Another aspect relates to a wireless communications apparatus thatincludes a memory and a processor. The memory retains instructionsrelated to determining that a message was not successfully read after afirst attempt, retaining the message as unreadable, and obtaining ascrambling information. The memory also retains instructions relating toattempting to re-read the message with the obtained scramblinginformation and ascertaining whether the message was not successfullyread after the first attempt due to a scrambling information change ordue to a reason not related to the scrambling information change. Theprocessor is coupled to the memory and configured to execute theinstructions retained in the memory.

A further aspect relates to a wireless communications apparatus thatfacilitates validation of messages. The apparatus includes a means fordetermining that a message was not successfully read after a firstattempt, a means for retaining the message as unreadable, and a meansfor obtaining scrambling information. The apparatus also includes ameans for attempting to re-read the message with the obtained scramblinginformation and a means for ascertaining whether the message was notsuccessfully read after the first attempt due to a scramblinginformation change or due to a reason different from the scramblinginformation change.

Yet another aspect relates to a machine-readable medium having storedthereon machine-executable instructions for validation of messages. Theinstructions include determining that a message was not successfullyread after a first attempt, retaining the message as unreadable, andobtaining a scrambling information. The instructions also includeattempting to re-read the message with the obtained scramblinginformation and ascertaining whether the message was not successfullyread after the first attempt due to a scrambling information change ordue to a reason different from the scrambling information change.

A further aspect relates to at least one processor for validatingmessages. The processor includes a first module operable to determinethat a message was not successfully read after a first attempt and asecond module operable to retain the message as unreadable. Theprocessor also includes a third module operable to obtain scramblinginformation and a fourth module operable to attempt to re-read themessage with the obtained scrambling information. The processor furtherincludes a fifth module operable to determine whether the message wasnot successfully read after the first attempt due to a scramblinginformation change or due to a reason not related to the scramblinginformation change.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of the variousaspects may be employed. Other advantages and novel features will becomeapparent from the following detailed description when considered inconjunction with the drawings and the disclosed aspects are intended toinclude all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication system in accordance withvarious aspects presented herein.

FIG. 2 illustrates a multiple access wireless communication systemaccording to one or more aspects.

FIG. 3 illustrates a system that validates stored or incoming messageswith related incoming or stored messages.

FIG. 4 illustrates an example of a structure of messages that are linkedtogether.

FIG. 5 illustrates an example schematic representation of linkingbetween overhead messages and a Quick Paging Channel (QPCH).

FIG. 6 illustrates a schematic representation of receiving an error on aQuick Page decode and updating the messages and subsequently re-decodingthe same bits correctly.

FIG. 7 illustrates details of a time line for a UMB system, althoughother systems can be utilized with the disclosed techniques.

FIG. 8 illustrates an example of potential time savings realized byutilizing cached System Information in accordance with one or more ofthe disclosed aspects.

FIG. 9 illustrates a method for validating stored and/or incomingmessages.

FIG. 10 illustrates a method for validating stored messages byutilization of related incoming messages.

FIG. 11 illustrates a method for validation of quick page messages bydecoding a new related message.

FIG. 12 illustrates a system that facilitates validating stored and/orincoming messages in accordance with one or more of the disclosedaspects.

FIG. 13 illustrates an exemplary wireless communication system.

FIG. 14 illustrates an example system that validates stored and/orincoming overhead messages.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details. In other instances,well-known structures and devices are shown in block diagram form inorder to facilitate describing these aspects.

As used in this application, the terms “component”, “module”, “system”,and the like are intended to refer to a computer-related entity, eitherhardware, firmware, a combination of hardware and software, software, orsoftware in execution. For example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on acomputing device and the computing device can be a component. One ormore components can reside within a process and/or thread of executionand a component may be localized on one computer and/or distributedbetween two or more computers. In addition, these components can executefrom various computer readable media having various data structuresstored thereon. The components may communicate by way of local and/orremote processes such as in accordance with a signal having one or moredata packets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across a networksuch as the Internet with other systems by way of the signal).

Furthermore, various aspects are described herein in connection with awireless terminal. A wireless terminal can also be called a system,subscriber unit, subscriber station, mobile station, mobile, mobiledevice, device remote station, remote terminal, access terminal, userterminal, terminal, wireless communication device, user agent, userdevice, or user equipment (UE). A wireless terminal may be a cellulartelephone, a cordless telephone, a Session Initiation Protocol (SIP)phone, a smart phone, a wireless local loop (WLL) station, a personaldigital assistant (PDA), a laptop, a handheld communication device, ahandheld computing device, a satellite radio, and/or another processingdevice for communicating over a wireless system. Moreover, variousaspects are described herein in connection with a base station. A basestation may be utilized for communicating with wireless terminal(s) andmay also be referred to as an access point, Node B, or some otherterminology.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches may also be used.

Referring now to FIG. 1, a wireless communication system 100 inaccordance with various aspects presented herein is illustrated. System100 can comprise one or more base stations 102 in one or more sectorsthat receive, transmit, repeat, and so forth, wireless communicationsignals to each other and/or to one or more mobile devices 104. Eachbase station 102 can comprise multiple transmitter chains and receiverchains (e.g., one for each transmit and receive antenna), each of whichcan in turn comprise a plurality of components associated with signaltransmission and reception (e.g., processors, modulators, multiplexers,demodulators, demultiplexers, antennas, and so forth). Each mobiledevice 104 can comprise one or more transmitter chains and receiverchains, which can be utilized for a multiple input multiple output(MIMO) system. Each transmitter and receiver chain can comprise aplurality of components associated with signal transmission andreception (e.g., processors, modulators, multiplexers, demodulators,demultiplexers, antennas, an so on), as will be appreciated by oneskilled in the art.

A base station 102 can convey initial information to the mobile devicesthrough over the air messages. In wireless communication systems thatlink these over the air messages, another over the air message canassist with validating and/or invalidating messages that were previouslyunreadable and, therefore, stored. In accordance with the disclosedaspects, the mobile device 104 is capable of re-using stored messages inthis manner and, thus, battery power and life can be extended.Additionally or alternatively, time can be saved because the need todecode additional messages can be mitigated. Further informationrelating to using messages to validate other messages according to thedisclosed aspects will be provided below.

Referring now to FIG. 2, a multiple access wireless communication system200 according to one or more aspects is illustrated. A wirelesscommunication system 200 can include one or more base stations incontact with one or more user devices. Each base station providescoverage for a plurality of sectors. A three-sector base station 202includes multiple antenna groups, one including antennas 204 and 206,another including antennas 208 and 210, and a third including antennas212 and 214. According to the figure, only two antennas are shown foreach antenna group, however, more or fewer antennas may be utilized foreach antenna group. Mobile device 216 is in communication with antennas212 and 214, where antennas 212 and 214 transmit information to mobiledevice 216 over forward link 220 and receive information from mobiledevice 216 over reverse link 218. Forward link (or downlink) refers tothe communication link from the base stations to mobile devices, and thereverse link (or uplink) refers to the communication link from mobiledevices to the base stations. Mobile device 222 is in communication withantennas 204 and 206, where antennas 204 and 206 transmit information tomobile device 222 over forward link 226 and receive information frommobile device 222 over reverse link 224.

Each group of antennas and/or the area in which they are designated tocommunicate may be referred to as a sector of base station 202. In oneor more aspects, antenna groups each are designed to communicate tomobile devices in a sector or the areas covered by base station 202. Abase station may be a fixed station used for communicating with theterminals.

In a conventional wireless communication system, a mobile device spendsa large amount of time in idle mode monitoring messages. The mobiledevice can monitor pages and over time might determine that the messagesare invalid (e.g., unreadable), thus the device will collect all themessages again. The messages can be sent according to a fixed schedule.If it is possible that a current message is out-of-date or otherwiseinvalid (e.g., unreadable), the device will typically wait to downloadthe entire message again and takes the time to decode the full message,which can waste resources.

The one or more disclosed aspects presented herein can allow the mobiledevice to save time by validating a stored message by decoding a relatedmessage, which can be received at a much quicker rate. In accordancewith some aspects, the mobile device can save time by validating apreviously unreadable message (that was retained in a storage media) bydecoding a new related message and subsequently re-reading the storedmessage or its CRC (cyclic redundancy check). One or more of thedisclosed aspects allow the stored message (or its CRC) be re-read byquickly updating the messages that could affect the stored message (orits CRC) through a scramble or signature match.

FIG. 3 illustrates a system 300 that validates stored or incomingmessages with related incoming or stored messages. In a wirelesscommunication system, a sender encodes a message, which is decoded orread at a receiver. If the receiver is not able to read a message, itcould indicate that a scrambling (e.g., encoding) of the message haschanged. If the scrambling of the message changed, the receiver needs toreceive the new scrambling information in order to successfully decodethe message. However, unsuccessful decoding might also be a result ofanother reason, such as environmental fading effects within the networkor other communication failure reasons (e.g., jamming). Scramblinginformation change and other reasons for unsuccessful decoding canappear as noise, therefore, it can be difficult in traditional systemsto distinguish the cause of the unsuccessful decode. System 300 can beconfigured to determine whether an unsuccessful decoding was a result ofa scrambling information change or a reason different from a scramblinginformation change. Further, system 300 can provide time savings byvalidating a stored message by decoding a related message, which can bedownloaded at a quicker rate.

System 300 includes an access point 302 that is in communication with amobile device 304. Although a number of access points 302 and mobiledevices 304 can be included in system 300, as will be appreciated, asingle access point 302 that is in communication with a single mobiledevice 304 is illustrated for purposes of simplicity.

The communication between access point 302 and mobile device 304 can bewireless or over the air. Some of the over the air messages between theaccess point 302 and the mobile device 304 can be sent frequently. Suchmessages inform the mobile device 304 about parameters or settings thatcan change quickly. Other over the air messages can be sent infrequentlybecause the information contained in these messages can be relativelyconstant. Such information in these infrequent messages can includeinformation about the network (e.g., access point 302) identification,the type of network and how to access it, parameters to utilize duringmobile device operation on the network, parameters specific to certainsectors of the network, as well as other information.

A procedure for providing the mobile device 304 a sense of confidence inthe messages received is to embed information about some of the messagesin each other. An example of this is a hierarchy scheme in which message“A” would have information about itself embedded in message “B”, andmessage “B” would have information about itself embedded in message “C”,and so forth. The embedded information can be performed in a number ofways, including a matched signature in both messages or scrambling of aCRC of each message using signatures or hashes of other messages, aswell as other techniques. Further detailed information relating tolinking of messages will be provided below with reference to FIG. 4 andFIG. 5.

In order to determine whether a received message could not be read as aresult of a signature information change or another reason (e.g.,environmental fading effects, jamming, the entire message was notreceived, and so forth), the mobile device 304 can include a decoder 306that can be configured to decode or read a previously encoded message,which could have been encoded by an encoder 308 of base station 302.Encoder 308 can modulate and/or encode signals in accordance with asuitable wireless communication protocol (e.g., OFDM, OFDMA, CDMA, TDMA,GSM, HSDPA, . . . ), which signals can then be transmitted to mobiledevice 304. Encoder 308 can be a voice coder (vocoder) that utilizes aspeech analyzer to convert analog waveforms into digital signals oranother type of encoder.

Upon successfully reading a message by decoder 306, an acknowledgment(ACK) can be generated. The ACK indicates a successful receipt of themessage and can be sent to base station 304 so that base station 304 isaware that the message was received and decoded or read, and thereforeneed not be retransmitted. In accordance with some aspects, a negativeacknowledgment (NACK) can be generated and sent if there was not asuccessful receipt of the message. The NACK can be sent to the basestation 302 to inform base station 302 that the message was successfullyreceived (e.g., read) by mobile device 304. Thus, base station 302 canretransmit the message, or a portion thereof, if further communicationof the message is to be transmitted.

If a message is not successfully decoded (resulting in a NACK) asdetermined by decoder 306, the entire unreadable message or bits frommessages that were not successfully read can be retained in a cache 310.The cache 310 can be any type of storage media or memory, as will bedescribed in further detail below. For example purposes and notlimitation, a quick page message can be stored in cache 310. The quickpage message, which was not successfully read, can be assumed to bevalid but the message utilized to scramble or signature match with thequick page message (or its CRC) is assumed to be invalid.

Also included in mobile device 304 is a scrambling information acquirer312 that can be configured to obtain scrambling information. Thescrambling information can be derived utilizing various technologiessuch as algorithms, hash algorithms, or other methods (e.g., utilizingcryptology keys). The scrambling information obtained can be the samescrambling information that might have been previously received (andutilized to read the unreadable messages) or it can be differentscrambling information (e.g., the scrambling information changed).

In accordance with some aspects, the scrambling information acquirer 312can obtain a Quick Channel Information (QuickChannelInfo) (QCI) Message,wherein the retained unreadable message is a quick page message and thequick page message is considered valid and a message (e.g., such as anoverhead message) used to scramble the quick page message is invalid.According to some aspects, this QCI message can be received in a firstportion of a subsequent superframe.

Decoder 306 can attempt to re-read the previously unreadable message orbits retained in cache 310 utilizing the newly obtained scramblinginformation. In accordance with some aspects, the scrambling informationis obtained from one source and the retained unreadable message is adifferent source.

A message verifier 314 can be configured to ascertain whether thepreviously unreadable message was not successfully read previously(before the newly obtained scrambling information) because of ascrambling information change or due to a reason not related to thescrambling information change (e.g., environmental fading effects,jamming, and so forth). Message verifier 314 can determine that, if themessages retained in the cache 310 can be successfully read by utilizingthe obtained scrambling information (e.g., different scramblinginformation), it indicates that the read attempt failed because thescrambling information changed. Further, message verifier 314 canascertain that the message was not previously read successfully due to areason other than a signature information change if an attempt tore-read the message succeeds with original scrambling information (e.g.,the same scrambling information utilized for the first read attempt).

In accordance with some aspects, the message verifier 314 can beconfigured to validate a stored quick page message by utilizing QCIMessage information to descramble a saved quick page CRC. However, itshould be understood that the disclosed aspects are not limited to atype of message, a message naming convention, nor a type ofcommunication system.

Attempting to re-read the saved, previously unreadable messages, canmitigate obtaining and attempting to read more messages than isnecessary, which can save battery life and other resources. Further, ifthe unreadable message or bits of the message that were unreadable aresaved in the cache 310, resources and time can be saved because theentire messages do not have to be once again be retrieved from theaccess point 302 (or other sender of the messages).

System 300 can include memory 316 operatively coupled to mobile device304. Memory 316 can be external to mobile device 304 or can residewithin mobile device 304. Memory 316 can store information related todetermining that a packet was not successfully read after at least afirst attempt, storing the unreadable message, receiving a scramblinginformation, attempting to re-read the message with the receivedscrambling information, and determining whether the message wasunreadable after the first attempt due to a change in the scramblinginformation or due to another reason(s). A processor 318 can beoperatively connected to mobile device 304 (and/or memory 316) tofacilitate analysis of information related to validation of stored orincoming messages in a communication network. Processor 318 can be aprocessor dedicated to analyzing and/or generating information receivedby mobile device 304, a processor that controls one or more componentsof system 300, and/or a processor that both analyzes and generatesinformation received by mobile device 304 and controls one or morecomponents of system 300.

Memory 316 can store protocols associated with validating stored and/orincoming messages, taking action to control communication between mobiledevice 304 and access point 302, and other functions, such that system300 can employ stored protocols and/or algorithms to achieve improvedcommunications in a wireless network as described herein. In accordancewith some aspects, memory 316 can include or be associated with thecache 310, as discussed above.

It should be appreciated that the data store (e.g., memories) componentsdescribed herein can be either volatile memory or nonvolatile memory, orcan include both volatile and nonvolatile memory. By way of example andnot limitation, nonvolatile memory can include read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of example and not limitation, RAM is available in many formssuch as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM(SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM),Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Memory 316 ofthe disclosed aspects are intended to comprise, without being limitedto, these and other suitable types of memory.

In order to fully appreciate the disclosed aspects, FIG. 4 illustratesan example of a structure of messages 400 that are linked together. Itshould be understood that the various examples provided herein mayrelate to a specific implementation in order to describe the variousaspects, however, the disclosed aspects are not limited to the specificimplementations herein described. Additionally, the examples of linkingof these messages is not limited to the types of messages nor the mannerin which they are linked as shown and described herein. In accordancewith the disclosed aspects, the linking of messages provides that onemessage can be utilized to determine the validity of other messages thathave previously been received.

The figure illustrates how a System Information (SystemInfo) Message402, a Quick Channel Information (QuickChannelInfo) (QCI) Message 404,an Extended Channel Information (ExtendedChannelInfo) (ECI) Message 406,and a Sector Parameters Message 408 can be linked together by varioussignatures, scrambling, hashes, or through other means. It should beunderstood that the messages that utilize the disclosed aspects can bedifferent message that perform other functions or messages that performsimilar functions as those illustrated but can be referred to withdifferent terminology.

The SystemInfo Message 402 can be transmitted in a Forward-PrimaryBroadCast Channel (F-PBCCH) of a superframe preamble or everysuperframe. For example, the F-PBCCH can be an OFDM symbol number “0” ofthe superframe preamble. In accordance with some aspects, it can takeabout sixteen superframes to transmit the entire SystemInfo Message 402.The start of the message can be in a superframe where SFIndex mod 16=0.SystemInfo Message 402 can have a SystemInfo signature field 410, whichcan be an assigned number.

The QuickChannelInfo (QCI) Message 404 can be transmitted in alternatesuperframes in a Forward—Secondary BroadCast Channel (F-SBCCH) of thesuperframe preamble. For example, the F-SBCCH can be in OFDM symbolsnumbers 1 through 4 of the superframe preamble. In synchronous mode, theQCI Message 404 can be transmitted in superframes with an even value ofPilotPhase. In asynchronous mode, QCI Message 404 can be transmitted insuperframes with an even value of SuperFrameIndex. The CRC of the QCIMessage 404 can be scrambled by the SystemInfo Signature 410. The QCIMessage 404 can include the Effective Number of Antennas 412 and theSSCH Number HopPorts 414, as well as other information.

The ECI Message 406 can be transmitted in PHY frames in Forward TrafficChannel MAC with BroadcastMacID. In accordance with some aspects, theECI Message 406 can be re-transmitted about every eight superframes.Fields included in the ECI Message 406 include a SectorParametersignature and an ECI signature field 416, which can be an assignedvalue. Also included can be a SectorInformation Group 418, anAccessParameterGroup 420, a PowerControlGroup 422, as well as otherinformation.

The SectorParameters Message 408 can be transmitted in PHY frames inForward Traffic Channel MAC with Broadcast MacID. The SectorParametersMessage 408 can be transmitted approximately every sixty-foursuperframes. A SectorParameters signature field, which can have anassigned value, is included in the SectorParameters Message 408. TheSectorParameters signature field of the ECI Message 406 and theSectorParameters Message 408 can be common. The SectorParameter Message408 can include a Neighbor List 424 and other information.

FIG. 5 illustrates an example schematic representation 500 of linking orconnection between overhead messages and a Quick Paging Channel (QPCH).It should be understood that the messages shown and described are forexample purposes and the aspects are not limited to these channels. Asillustrated, the Sector Parameter (SecParam) message can include asignature 502. A signature is an identifier that specifies the contentsof a message. For example, the signature can be a unique number. Thesignature can be derived from a formula, algorithm, hashing algorithm,or other technique for deriving an identifier that corresponds to amessage.

The SecParam signature 502 can be included in the payload information ofan ExtendedChannelInfo (ECI) message (e.g., ECI block), as shown atarrow 504. The ECI message also includes a signature 506. When the ECImessage is decoded, the signature 506 is checked and, if it matches thesignature for the SecParam message that is stored in memory or cache, itis valid. It is inferred that it is valid because the signature shouldguarantee its uniqueness. If the ECI message and the signature aredifferent than the one retained in cache, the information in the cacheis invalid and another message should be retrieved.

A hash algorithm can be applied to the ECI message and the CRC can bescrambled, which is the scrambling of a QPCH message 508. The CRC canalso be scrambled with quick channel information (QuickChannelInfo)(QCI) 510. A system information (SystemInfo) (SysInfo) message (and itssignature 512) and the QCI 510 have a relationship similar to that ofthe SecParam 502 and the ECI 506. The QCI can include a field, which caninclude the signature for the SysInfo 512. The QPCH CRC 508 is scrambledwith the ECI signature 506 and a hash of the QCI 510.

At substantially the same time as the QPCH message is received at adevice it is decoded and verified against its CRC to determine if it wasread correctly. The CRC fails if the ECI 506 and/or the QCI 510 changed.However, all the bits could have been decoded correctly and the onlyerror was that the CRC is the incorrect CRC because it is scrambled.

For example, the device retrieves the QCI message and realizes that itchanged. The device then verifies the QPCH CRC 508. A verification canindicate that the ECI message is correct and the Sector Parametersmessage for it is correct. When the QCI message is retrieved and it didnot change anything with the system information message, it indicatesthat the systems information message is correct. Thus by simply checkingone message, the mobile device is able to decode the QPCH message bydescrambling the CRC and is able to validate the entire chain. Thisresults in a savings because the ECI messages are expensive in thatthese message take a long time to transmit/receive over the air and itis a large message that is sent infrequently. However, the QCI messagesare less expensive, shorter, and can be sent every other superframe(e.g., every 15 msec). Thus, a standby time savings can be realized bychecking the CQI, revalidating the CPCH and retaining the ECI message inall cases except where it changes. By being able to decode the QPCHsuccessfully, it can be inferred that the sector parameters informationdid not change either.

In accordance with the disclosed aspects, linking the messages in suchdetail provides that one message can ultimately be utilized to determinea validity of other messages that have previously been collected. In anUltra Mobile Broadband (UMB) case, for example, if the signatureembedded in a newly received ECI does not match a signature in apreviously collected SecParams, then it might be concluded that theSecParams has changed and should be updated. Similarly, if the QCI CRCcannot be descrambled, it can be concluded that the SysInfo signaturehas changed and the SysInfo should be updated.

Meanwhile, a QPCH error can indicate a number of possibilities. Onepossibility is that the received signal strength might have been bad atthe time the QPCH was received at the mobile device and there were notenough received bits to decode the message properly. Another possibilityis that the ECI message has changed and, therefore, the ECI signatureutilized to scramble the QPCH CRC is incorrect. Another possibility isthat the QCI message has changed and, therefore, the hash of the QCIutilized to scramble the QPCH CRC is incorrect. This last possibilitywill be utilized below to describe how the information can be utilizedto increase a standby time of a mobile device. In a further possibility,a mobile device (such as a UMB mobile device) might be able to utilizethe ability to successfully descramble a QCI CRC as a validation of acached SysInfo Message, which will be described with reference to FIG. 8below.

With reference now to FIG. 6 illustrated is a Generic Quick Page (QP)Re-Decode 600. In a generic case of the QP being decoded in error, thereare a variety of options available to the mobile device, depending onthe type of system being utilized. An option can be to decode a secondQP bit. Another option that can be utilized is to ignore the QPinformation completely and proceed to decode the Fast Page (FP) directlyto check for an incoming page. A further option is to store the raw QPdata bits and then update any overhead messages that may have changedand resulted in the QP error. If the overall impact to the mobiledevice's standby time is favorable, it can increase the standby time.

FIG. 6 illustrates a schematic representation 600 of receiving an erroron a QP decode and then updating the overhead messages and subsequentlyre-decoding the same bits correctly. The schematic representation 600 isfor a generic QP re-decode. The decode of the QP data is illustrated, at602. The raw data can be stored in a storage media, such as memory (orcache), upon decode or a CRC failure. At 604, additional overheadmessages can be decoded. These messages can be utilized, at 606, wherethe QP data that was stored is re-decoded or its CRC is checked with newinformation gained, at 604. At 608, the FP can be decoded if the QPre-decode was not enabled, indicated a page, or failed again.

FIG. 7 illustrates details of a time line 700 for a UMB system, althoughother systems can be utilized with the disclosed techniques. Asillustrated, QPC and QCI messages are sent in alternating superframes702 and 704. These superframes 702 and 704, in accordance with someaspects, can each be approximately 20 msec in length. Both the QPC andQCI can be sent in a preamble portion of the superframe, which canentail approximately the first msec of the superframe. The preamble canalso contain information that the mobile device utilizes to update thetiming of the mobile device and to determine which sectors should beutilized for receiving data from an access point. Thus, the mobiledevice can process the preamble for a superframe of interest. In theexample UMB system, the FP can occur in the superframe immediatelyfollowing the superframe with the QPCH. Thus updating the QCI messagemight not incur additional loss of standby time for the mobile device.

As illustrated, at 704, the QP data in the superframe preamble isdecoded. The data can be stored if the CRC check fails. At 709, the QCImessage is decoded in the next superframe preamble. The message can bedecoded here because the mobile device is already awake for thissuperframe preamble. At 710, the QPCH CRC can be re-checked based on thehash of the new QCI. The mobile device does not have to decode the FP if“no page” is determined. The FP can be decoded, at 712, if necessary. Byupdating the QCI and subsequently being able to possibly validate theQPCH CRC, the mobile device does not need to be powered on to receivethe FP, if the QPCH result indicated “no page.” This can result in apower savings for the mobile device and an increase in standby time.

FIG. 8 illustrates an example of time savings 800 utilizing cachedSysInfo in accordance with one or more of the disclosed aspects. When anaccess terminal initially finds a sector to acquire the access node, theSysInfo message can be the first message sought. The SysInfo message canbe sent in portions across about sixteen superframes, illustrated assuperframes 0, 1, 2, through 15. The QCI message can be sent in itsentirety in each superframe. A few QCI messages are labeled at 802 and804. In this example, each superframe can take about 20 msecs, which isillustrated by arrow 806. It can take approximately 320 msecs for theentire message to be received, in one example. By utilizing a cachedSysInfo message from a previous access node connection, the accessterminal can directly attempt to decode the QCI and utilize the storedSysInfo's signature to descramble the QCI CRC. If the CRC passes, theSysInfo message stored in cache is validated and does not need to berecollected. Since the QCI can be completely decoded in any superframe,the access terminal can reach the idle state about 300 msec sooner andcan save, in this example, fifteen additional superframe wakeups ofbatter power. Thus, about 300 msec, illustrated at 808, can be saved byusing cached SysInfo. However, it should be understood that this timesavings 800 is for illustrative purposes to show a few of the advantagesof the disclosed aspects and various systems can realize less or moresavings.

In view of the exemplary systems shown and described above,methodologies that may be implemented in accordance with the disclosedsubject matter, will be better appreciated with reference to thefollowing flow charts. While, for purposes of simplicity of explanation,the methodologies are shown and described as a series of blocks, it isto be understood and appreciated that the claimed subject matter is notlimited by the number or order of blocks, as some blocks may occur indifferent orders and/or at substantially the same time with other blocksfrom what is depicted and described herein. Moreover, not allillustrated blocks may be required to implement the methodologiesdescribed hereinafter. It is to be appreciated that the functionalityassociated with the blocks may be implemented by software, hardware, acombination thereof or any other suitable means (e.g. device, system,process, component). Additionally, it should be further appreciated thatthe methodologies disclosed hereinafter and throughout thisspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methodologies tovarious devices. Those skilled in the art will understand and appreciatethat a methodology could alternatively be represented as a series ofinterrelated states or events, such as in a state diagram.

FIG. 9 illustrates a method 900 for validating stored and/or incomingmessages. Method 900 can be utilized in a wireless communicationenvironment in order to more efficiently make a determination whethermessages were not read successfully due to a scrambling informationchange or due to another reason, since these problems might appearsimilar because the packets could not be successfully read.

For example, in a wireless communication environment there can bedevices that are on the fringe of the geographic area or cell served bya serving base station. In fringe type environments there can be a largeamount of fading occurring due to the nature of such environments.Instead of needing to constantly obtain message to determine that amessage previously received was correct (e.g., no scrambling informationchange), method 900 can allow a device to backup and revalidate messagesquicker, which can save standby time in harsh fading environments.

Method 900 begins at 902, when a message is not successfully read due toan unknown reason (e.g., scrambling information change, jamming,environmental fading effects, and so forth). The unreadable message canbe retained, at 904, in a storage media, such as a cache or memory.Saving the unreadable message can mitigate the amount of time andresources necessary to retrieve the entire message at a later time. At906, scrambling information is obtained. This scrambling information canbe received infrequency or it might take longer to download than othertypes of information. This scrambling information is applied to one ormore of the retained previously unreadable messages, at 908 with anattempt to re-read the message.

A determination is made, at 910, whether the attempt to re-read thepreviously unreadable message with the newly obtained scramblinginformation (e.g., different scrambling information) was successful. Ifthe decode attempt was successful (“YES”) with the newly obtainedscrambling information it can indicate, at 912, that the scramblinginformation was changed for the previously non-decoded packets. If thedecode attempt was not successful (“NO”), it can indicate, at 914, thatthe scrambling information was not a factor that caused the unsuccessfulread attempt (e.g., both the old and the most recently obtainedscrambling information was not able to decode the packet). In thissituation, the unsuccessful read attempt might have been caused byenvironmental fading effects or other communication problems. Anotherattempt to re-read the message with the original scrambling information(e.g. the information utilized for the first read attempt) can beconducted. If the attempt to re-read the message with the originalsignature information (e.g., signature information utilized to read themessage during the first attempt) is successfully, it indicates failuredue to a reason other than a signature information change.

FIG. 10 illustrates a method 1000 for validating stored messages byrelated incoming messages. When a mobile device listens to a wirelesscommunications network, some of the messages may take a relatively longtime to download. When messages are linked through signatures, hashes,or other methods, the stored messages can be validated by decodingsubsequent messages, which might be received at a quicker rate. Thus,method 1000 can mitigate the time spent downloading larger messages,which can result in an increased standby time and increased performancemetrics, such as call reception.

For example purposes and not limitation, in a UMB system, a QCI messagecan be gathered within a maximum of about 40 msecs and, if decodecorrectly with a stored System Info message, can save approximately 320msecs of time to gather a new System Info message.

Method 1000 starts, at 1002, when an message's signature is stored. Inaccordance with some aspects, something other than the signature isstored, depending on what is applicable to a given system. A subsequentmessage is received at 1004. This subsequent message might be receivedmuch quicker than other messages. At 1006, the stored message'ssignature is utilized to decode the received message. A determination ismade, at 1008, whether the decode was successful. If the decode issuccessful (“YES”) the decode validates the stored message, at 1012. Ifthe decode is not successful (“NO”), at 1014, the stored message cannotbe validated and a newer message might need to be obtained.

FIG. 11 illustrates a method 1100 for validation of quick page messagesby decoding a new related overhead message. It should be understood thatthat the method and messages discussed with reference to this figure arefor purposes of understanding and not limitation. Method starts at 1102when a quick page message is stored. This stored quick page message isassumed to be valid, however, the overhead message which was used toscramble or signature match with the quick page (or its CRC) is assumedto be invalid. This overhead can be updated while mitigating the amountof additional resources utilized by receiving a next superframe (in aUMB system) and decoding the QCI message, at 1104. The quick page CRCcan be descrambled, at 1106, with this new information. Since the mobiledevice listens to this part of the superframe where the QCI occurs (thefull page occurs later in the same superframe), thus mitigatingadditional cost to the mobile device. Thus, method 1100 allows thestored quick page to be re-checked, potentially saving a subsequentdecode of the full page message.

With reference now to FIG. 12, illustrated is a system 1200 thatfacilitates validating stored and/or incoming messages in accordancewith one or more of the disclosed aspects. System 1200 can reside in auser device. System 1200 comprises a receiver 1202 that can receive asignal from, for example, a receiver antenna. The receiver 1202 canperform typical actions thereon, such as filtering, amplifying,downconverting, etc. the received signal. The receiver 1202 can alsodigitize the conditioned signal to obtain samples. A demodulator 1204can obtain received symbols for each symbol period, as well as providereceived symbols to a processor 1206.

Processor 1206 can be a processor dedicated to analyzing informationreceived by receiver component 1202 and/or generating information fortransmission by a transmitter 1208. In addition or alternatively,processor 1206 can control one or more components of user device 1200,analyze information received by receiver 1202, generate information fortransmission by transmitter 1208, and/or control one or more componentsof user device 1200. Processor 1206 may include a controller componentcapable of coordinating communications with additional user devices.

User device 1200 can additionally comprise memory 1208 operativelycoupled to processor 1206 and that can store information related tocoordinating communications and any other suitable information. Memory1210 can additionally store protocols associated with samplerearrangement. It will be appreciated that the data store (e.g.,memories) components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory.By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). The memory 1208 of the subject systems and/ormethods is intended to comprise, without being limited to, these and anyother suitable types of memory. User device 1200 can further comprise asymbol modulator 1212 and a transmitter 1208 that transmits themodulated signal.

Receiver 1202 is further operatively coupled to an obtainer 1214 thatcan be configured to obtain new scrambling information. In accordancewith some aspects, the scrambling information can be obtained from onesource, wherein the retained unreadable message is obtained from adifferent source. If the demodulator 1204 cannot successfully demodulate(e.g., read) a received message, the message, or the unsuccessfully readbits can be retained in memory 1210. At substantially the same time asobtaining the new scrambling information, demodulator 1204 can attemptto re-read the saved message and/or bits. A verifier 1216 can beconfigured to determine, based on the re-read attempt with the obtainedscrambling information, whether the packet was previously not able to bedemodulated based on a scrambling information change or based on areason not related to the scrambling information change (e.g., jamming,environmental fading effects).

FIG. 13 illustrates an exemplary wireless communication system 1300.Wireless communication system 1300 depicts one base station and oneterminal for sake of brevity. However, it is to be appreciated thatsystem 1300 can include more than one base station or access pointand/or more than one terminal or user device, wherein additional basestations and/or terminals can be substantially similar or different fromthe exemplary base station and terminal described below. In addition, itis to be appreciated that the base station and/or the terminal canemploy the systems and/or methods described herein to facilitatewireless communication there between.

Referring now to FIG. 13, on a downlink, at access point 1305, atransmit (TX) data processor 1310 receives, formats, codes, interleaves,and modulates (or symbol maps) traffic data and provides modulationsymbols (“data symbols”). A symbol modulator 1315 receives and processesthe data symbols and pilot symbols and provides a stream of symbols. Asymbol modulator 1315 multiplexes data and pilot symbols and obtains aset of N transmit symbols. Each transmit symbol may be a data symbol, apilot symbol, or a signal value of zero. The pilot symbols may be sentcontinuously in each symbol period. The pilot symbols can be frequencydivision multiplexed (FDM), orthogonal frequency division multiplexed(OFDM), time division multiplexed (TDM), frequency division multiplexed(FDM), or code division multiplexed (CDM).

A transmitter unit (TMTR) 1320 receives and converts the stream ofsymbols into one or more analog signals and further conditions (e.g.,amplifies, filters, and frequency upconverts) the analog signals togenerate a downlink signal suitable for transmission over the wirelesschannel. The downlink signal is then transmitted through an antenna 1325to the terminals. At terminal 1330, an antenna 1335 receives thedownlink signal and provides a received signal to a receiver unit (RCVR)1340. Receiver unit 1340 conditions (e.g., filters, amplifies, andfrequency downconverts) the received signal and digitizes theconditioned signal to obtain samples. A symbol demodulator 1345 obtainsN received symbols and provides received pilot symbols to a processor1350 for channel estimation. Symbol demodulator 1345 further receives afrequency response estimate for the downlink from processor 1350,performs data demodulation on the received data symbols to obtain datasymbol estimates (which are estimates of the transmitted data symbols),and provides the data symbol estimates to an RX data processor 1355,which demodulates (i.e., symbol demaps), deinterleaves, and decodes thedata symbol estimates to recover the transmitted traffic data. Theprocessing by symbol demodulator 1345 and RX data processor 1355 iscomplementary to the processing by symbol modulator 1315 and TX dataprocessor 1310, respectively, at access point 1305.

On the uplink, a TX data processor 1360 processes traffic data andprovides data symbols. A symbol modulator 1365 receives and multiplexesthe data symbols with pilot symbols, performs modulation, and provides astream of symbols. A transmitter unit 1370 then receives and processesthe stream of symbols to generate an uplink signal, which is transmittedby the antenna 1335 to the access point 1305.

At access point 1305, the uplink signal from terminal 1330 is receivedby the antenna 1325 and processed by a receiver unit 1375 to obtainsamples. A symbol demodulator 1380 then processes the samples andprovides received pilot symbols and data symbol estimates for theuplink. An RX data processor 1385 processes the data symbol estimates torecover the traffic data transmitted by terminal 1330. A processor 1390performs channel estimation for each active terminal transmitting on theuplink.

Processors 1390 and 1350 direct (e.g., control, coordinate, manage, . .. ) operation at access point 1305 and terminal 1330, respectively.Respective processors 1390 and 1350 can be associated with memory units(not shown) that store program codes and data. Processors 1390 and 1350can also perform computations to derive frequency and impulse responseestimates for the uplink and downlink, respectively.

For a multiple-access system (e.g., FDMA, OFDMA, CDMA, TDMA, and thelike), multiple terminals can transmit concurrently on the uplink. Forsuch a system, the pilot subbands may be shared among differentterminals. The channel estimation techniques may be used in cases wherethe pilot subbands for each terminal span the entire operating band(possibly except for the band edges). Such a pilot subband structurewould be desirable to obtain frequency diversity for each terminal. Thetechniques described herein may be implemented by various means. Forexample, these techniques may be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitsused for channel estimation may be implemented within one or moreapplication specific integrated circuits (ASICs), digital signalprocessors (DSPs), digital signal processing devices (DSPDs),programmable logic devices (PLDs), field programmable gate arrays(FPGAs), processors, controllers, micro-controllers, microprocessors,other electronic units designed to perform the functions describedherein, or a combination thereof. With software, implementation can bethrough modules (e.g., procedures, functions, and so on) that performthe functions described herein. The software codes may be stored inmemory unit and executed by the processors 1390 and 1350.

With reference to FIG. 14, illustrated is an example system 1400 thatvalidates stored and/or incoming messages. System 1400 can reside atleast partially within a mobile device. It is to be appreciated thatsystem 1400 is represented as including functional blocks, which may befunctional blocks that represent functions implemented by a processor,software, or combination thereof (e.g., firmware).

System 1400 includes a logical grouping 1402 of electrical componentsthat can act separately or in conjunction. Logical grouping 1402 caninclude an electrical component for determining that a message was notsuccessfully read after a first attempt 1404. Further, logical grouping1402 can comprise an electrical component for retaining the unreadablemessage 1406. For example, the unreadable message can be retained insystem memory. Moreover, logical grouping 1402 can include an electricalcomponent for obtaining a scrambling information 1408. In accordancewith some aspects, the scrambling information can be obtained from afirst source, wherein the retained unreadable message is a from a secondsource.

Electrical component for determining that a message was not successfullyread after a first attempt 1204 can attempt to re-read the saved messagewith the recently obtained scrambling information. An electricalcomponent for ascertaining why the message was not successfully read onthe first attempt 1410 can be included in logical grouping 1402. Themessage might not have been read due to a scrambling information changeor a reason not related to the scrambling information change. Inaccordance with some aspects, it can be ascertained that the message wasnot successfully read after the first attempt due to a scramblinginformation change if the second attempt to re-read the message issuccessful. In accordance with other aspects, it can be ascertained thatthe message was not successfully read after the first reading attemptdue to a reason other than a signature information check if the re-readattempt with the original signature information (e.g., the signatureinformation used for the first read attempt) is successful. According tosome aspects, the previously unreadable message is validated if there-read attempt is successful.

Additionally, system 1400 can include a memory 1412 that retainsinstructions for executing functions associated with electricalcomponents 1404, 1406, 1408, and 1410 or other components. While shownas being external to memory 1412, it is to be understood that one ormore of electrical components 1404, 1406, 1408, and 1410 may existwithin memory 1412.

It is to be understood that the aspects described herein may beimplemented by hardware, software, firmware, middleware, microcode, orany combination thereof. When the systems and/or methods are implementedin software, firmware, middleware or microcode, program code or codesegments, they may be stored in a machine-readable medium, such as astorage component. A code segment may represent a procedure, a function,a subprogram, a program, a routine, a subroutine, a module, a softwarepackage, a class, or any combination of instructions, data structures,or program statements. A code segment may be coupled to another codesegment or a hardware circuit by passing and/or receiving information,data, arguments, parameters, or memory contents. Information, arguments,parameters, data, etc. may be passed, forwarded, or transmitted usingany suitable means including memory sharing, message passing, tokenpassing, network transmission, etc.

The various illustrative logics, logical blocks, modules, and circuitsdescribed in connection with the aspects disclosed herein may beimplemented or performed with a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but, in the alternative, the processor may be any conventionalprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may comprise one or more modules operable to perform one ormore of the steps and/or actions described above.

For a software implementation, the techniques described herein may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. The software codes may be storedin memory units and executed by processors. The memory unit may beimplemented within the processor or external to the processor, in whichcase it can be communicatively coupled to the processor through variousmeans as is known in the art. Further, at least one processor mayinclude one or more modules operable to perform the functions describedherein.

Moreover, various aspects or features described herein may beimplemented as a method, apparatus, or article of manufacture usingstandard programming and/or engineering techniques. The term “article ofmanufacture” as used herein is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media. Forexample, computer-readable media can include but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips,etc.), optical disks (e.g., compact disk (CD), digital versatile disk(DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card,stick, key drive, etc.). Additionally, various storage media describedherein can represent one or more devices and/or other machine-readablemedia for storing information. The term “machine-readable medium” caninclude, without being limited to, wireless channels and various othermedia capable of storing, containing, and/or carrying instruction(s)and/or data. Additionally, a computer program product may include acomputer readable medium having one or more instructions or codesoperable to cause a computer to perform the functions described herein.

Further, the steps and/or actions of a method or algorithm described inconnection with the aspects disclosed herein may be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module may reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of storage mediumknown in the art. An exemplary storage medium may be coupled to theprocessor, such that the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium may be integral to the processor. Further, in some aspects, theprocessor and the storage medium may reside in an ASIC. Additionally,the ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal. Additionally, in some aspects, the steps and/or actionsof a method or algorithm may reside as one or any combination or set ofcodes and/or instructions on a machine readable medium and/or computerreadable medium, which may be incorporated into a computer programproduct.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM□, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTEand GSM are described in documents from an organization named “3rdGeneration Partnership Project” (3GPP). Additionally, cdma2000 and UMBare described in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). Further, such wireless communicationsystems may additionally include peer-to-peer (e.g., mobile-to-mobile)ad hoc network systems often using unpaired unlicensed spectrums, 802.xxwireless LAN, BLUETOOTH and any other short- or long-range, wirelesscommunication techniques.

While the foregoing disclosure discusses illustrative aspects and/oraspects, it should be noted that various changes and modifications couldbe made herein without departing from the scope of the described aspectsand/or aspects as defined by the appended claims. Accordingly, thedescribed aspects are intended to embrace all such alterations,modifications and variations that fall within scope of the appendedclaims. Furthermore, although elements of the described aspects and/oraspects may be described or claimed in the singular, the plural iscontemplated unless limitation to the singular is explicitly stated.Additionally, all or a portion of any aspect and/or aspect may beutilized with all or a portion of any other aspect and/or aspect, unlessstated otherwise.

To the extent that the term “includes” is used in either the detaileddescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim. Furthermore, the term“or” as used in either the detailed description of the claims is meantto be a “non-exclusive or”.

What is claimed is:
 1. A method for validating stored or incomingmessages, comprising: determining, by a decoder of a mobile device, thata message was not successfully read after a first attempt, wherein themessage was attempted to be read in the first attempt using firstscrambling information; retaining the message as unreadable in a cacheof the mobile device; obtaining second scrambling information related tothe retained message at a scrambling information acquirer of the mobiledevice; attempting, by the decoder, to re-read the retained message withthe second scrambling information from the cache; determining, by amessage verifier of the mobile device, whether the attempt to re-readthe retained message with the second scrambling information issuccessful; and if the attempt to re-read the retained message with thesecond scrambling information is successful, then determining, by themessage verifier, that the first attempt was not successful because of ascrambling information change, and otherwise determining that the firstattempt was not successful due to a reason different from the scramblinginformation change, wherein it is ascertained that the message was notsuccessfully read after the first attempt due to the reason differentfrom the scrambling information change if an attempt to re-read theretained message succeeds with the first scrambling information.
 2. Themethod of claim 1, wherein the unreadable message is validated if there-read attempt is successful.
 3. The method of claim 1, wherein thesecond scrambling information is obtained from a first source, andwherein the retained unreadable message is a different source.
 4. Awireless communications apparatus, comprising: a memory that retainsinstructions related to determining that a message was not successfullyread after a first attempt, wherein the message was attempted to be readin the first attempt using first scrambling information, retaining themessage as unreadable in a cache, obtaining second scramblinginformation related to the retained message, attempting to re-read theretained message with the second scrambling information from the cache,determining whether the attempt to re-read the retained message with thesecond scrambling information is successful, and if the attempt tore-read the retained message with the second scrambling information issuccessful, then determining that the first attempt was not successfulbecause of a scrambling information change, and otherwise determiningthat the first attempt was not successful due to a reason not related tothe scrambling information change, wherein the message was notsuccessfully read after the first attempt due to the reason not relatedto the scrambling information change if an attempt to re-read theretained message succeeds with the first scrambling information; and aprocessor, coupled to the memory, configured to execute the instructionsretained in the memory.
 5. The wireless communications apparatus ofclaim 4, wherein the unreadable message is validated if the re-readattempt is successful.
 6. The wireless communications apparatus of claim4, wherein the second scrambling information is obtained from a firstsource, and wherein the retained unreadable message is a differentsource.
 7. A wireless communications apparatus that facilitatesvalidation of messages, comprising: means for determining that a messagewas not successfully read after a first attempt, wherein the message wasattempted to be read in the first attempt using first scramblinginformation; means for retaining the message as unreadable in a cache;means for obtaining second scrambling information related to theretained message; means for attempting to re-read the retained messagewith the second scrambling information from the cache; means fordetermining whether the attempt to re-read the retained message with thesecond scrambling information is successful; and means for determiningthat the first attempt was not successful because of a scramblinginformation change if the attempt to re-read the retained message withthe second scrambling information is successful, and for otherwisedetermining that the first attempt was not successful due to a reasondifferent from the scrambling information change, wherein the messagewas not successfully read after the first attempt due to the reasondifferent from the scrambling information change if an attempt tore-read the retained message succeeds with the first scramblinginformation.
 8. The wireless communications apparatus of claim 7,wherein the unreadable message is validated if the re-read attempt issuccessful.
 9. The wireless communications apparatus of claim 7, whereinthe second scrambling information is obtained from a first source, andwherein the retained unreadable message is a different source.
 10. Anon-transitory machine-readable medium having stored thereonmachine-executable instructions for validation of messages, comprising:determining that a message was not successfully read after a firstattempt, wherein the message was attempted to be read in the firstattempt using first scrambling information; retaining the message asunreadable in a cache; obtaining second scrambling information relatedto the retained message; attempting to re-read the retained message withthe second scrambling information from the cache; determining whetherthe attempt to re-read the retained message with the second scramblinginformation is successful; and if the attempt to re-read the retainedmessage with the second scrambling information is successful, thendetermining that the first attempt was not successful because of ascrambling information change, and otherwise determining that the firstattempt was not successful due to a reason different from the scramblinginformation change, wherein the instructions further comprisedetermining that the message was not successfully read after the firstattempt due to a reason different from the scrambling information changeif an attempt to re-read the retained message succeeds with the firstscrambling information.
 11. The non-transitory machine-readable mediumof claim 10, wherein the unreadable message is validated if the re-readattempt is successful.
 12. The non-transitory machine-readable medium ofclaim 10, wherein the second scrambling information is obtained from afirst source, and wherein the retained unreadable message is a differentsource.
 13. At least one processor for validating messages, comprising:a computing device; a first module operable to determine that a messagewas not successfully read after a first attempt, wherein the message wasattempted to be read in the first attempt using first scramblinginformation; a second module operable to retain the message asunreadable in a cache; a third module operable to obtain secondscrambling information related to the retained message; a fourth moduleoperable to attempt to re-read the retained message with the secondscrambling information from the cache; and a fifth module operable todetermine whether the attempt to re-read the retained message with thesecond scrambling information is successful and if the attempt tore-read the retained message with the second scrambling information issuccessful, then determine that the first attempt was not successfulbecause of a scrambling information change, and otherwise determine thatthe first attempt was not successful due to a reason not related to thescrambling information change, wherein it is ascertained that themessage was not successfully read after the first attempt due to areason not related to the scrambling information change if an attempt tore-read the retained message succeeds with the first scramblinginformation.